Image Capture to Provide Advanced Features for Configuration of a Wearable Device

ABSTRACT

In one embodiment, a method for providing enhanced configuration features includes receiving, by a computing device, indication that a wearable device has started a pairing process with a second electronic device and obtaining images corresponding to the wearable device. Moreover, the method includes analyzing, by the computing device, the images to determine one or more aspects of the wearable device and configuring the wearable device using the one or more aspects of the wearable device.

INCORPORATION BY REFERENCE; DISCLAIMER

Each of the following applications are hereby incorporated by reference:application Ser. No. 16/425,291 filed on May 29, 2019; application No.62/679,928 filed on Jun. 3, 2018. The Applicant hereby rescinds anydisclaimer of claim scope in the parent application(s) or theprosecution history thereof and advises the USPTO that the claims inthis application may be broader than any claim in the parentapplication(s).

TECHNICAL FIELD

The disclosure generally relates to electronic devices, and morespecifically to providing configuration features for a wearableelectronic device using images captured of the wearable device.

BACKGROUND

Wearable devices have become commonplace in today's society, withvarious formfactors being available for purchase, includingwristwatches, glasses, rings, clothing, shoes, etc. Uses and functionsof these wearable devices vary greatly, as each wearable device may beworn at a different part of the body and/or on clothing and accessories,may include more or less functionality, may have more or less advancedhardware, may include more or less intuitive interface(s), etc. Theproliferation of these various wearable devices has resulted in manydifferent versions of processes for establishing a connection between awearable device and another electronic device. In order to initiallyestablish this coupling, a pairing process is performed on the wearabledevice and/or on the other electronic device.

In particular, among wearable devices, a smartwatch may beelectronically coupled with an external electronic device, such as asmartphone, via one or more wireless communication techniques, e.g.,radio frequency (RF), optical or light transmission, etc. However, eachpairing process typically requires extensive interaction and input froma user to properly set up the wearable device for the first time, sothat it is able to access wireless network(s) and/or interact with theother electronic device for uploading data, downloading data, andgenerally transferring information.

Moreover, many wearable devices have a user account associated therewiththat is specific to the user of the wearable device, and in order forthe wearable device to communicate with the other electronic device, thedevice is initially paired to an online account and/or to the otherelectronic device. Typically, this involves authentication, and alsoidentification or verification of the wearable device to be paired.Authentication includes verifying that the user is authorized to accessthe account to which data will be transmitted to/from the wearabledevice.

It is desirable to minimize the amount of user interaction and inputrequired in the pairing process and configuration for ease of use andsetup of the wearable device. This is particularly true of small formfactor wearable devices which are intentionally configured to minimizethe inclusion of external mechanical interface elements, such asbuttons, displays, and keys.

SUMMARY

In some implementations, a method for providing enhanced configurationfeatures includes receiving, by a computing device, indication that awearable device has started a pairing process with a second electronicdevice and obtaining images corresponding to the wearable device.Moreover, the method includes analyzing, by the computing device, theimages to determine one or more aspects of the wearable device andconfiguring the wearable device using the one or more aspects of thewearable device.

Particular implementations provide at least the following advantages.The user of the wearable device does not need to input various detailsabout the wearable device into the second electronic device in thepairing process or during configuration of the wearable device, as thesedetails are provided to the second electronic device as a result ofanalyzing the images, thereby providing an easier and more efficientpairing process. Moreover, aspects of the wearable device may further beused to configure the wearable device and to provide suggestions to theuser as to how the wearable device may be better utilized based onanalysis of the images.

Details of one or more implementations are set forth in the accompanyingdrawings and the description below. Other features, aspects, andpotential advantages will be apparent from the description and drawings,and from the claims.

DESCRIPTION OF DRAWINGS

FIG. 1 is a simplified block diagram of an example system for providingadvanced features for a pairing process of a wearable device.

FIG. 2 is a simplified diagram of an example electronic device capturingimage(s) of an example wearable device.

FIG. 3 shows four example orientations for a particular wearable device,in one implementation.

FIG. 4 is flow diagram of an example method for utilizing capturedimages to configure a wearable device.

FIG. 5 is flow diagram of an example method for utilizing imagescaptured for a paring process.

FIG. 6 is flow diagram of an example method for utilizing imagescaptured for a paring process.

FIG. 7 is a block diagram of an example computing device that isconfigured to implement features and processes of FIGS. 1-6.

Like reference symbols in the various drawings indicate like elements.

DETAILED DESCRIPTION

FIG. 1 is a block diagram of an example system 100 for providingadvanced features for a pairing process between a wearable device 114and a second electronic device 102, possibly utilizing a network 122.

The wearable device 114 comprises a processor or multiple processors andlogic and/or instructions configured to cause the processor(s) toperform operations, described in more detail in FIGS. 4-6. Referringagain to FIG. 1, in one implementation, the wearable device 114 is anelectronic device that is configured and designed to be worn by a userand/or on an article of clothing of a user, such as a shoe, a jacket, ashirt, underwear, etc. The wearable device 114 may be worn on a wrist ofthe user, around a neck of the user, on a finger of the user, on someother body part of the user, held by the user, and/or accessible by theuser remotely from other electronic devices.

The wearable device 114 may be any type of wearable or portable deviceknown in the art, such as a smartwatch, an activity and/or fitnesstracker (including electronic trackers worn as a wristband, as a ring ona finger, in a shoe, on clothing, on a hat, etc.), virtual reality (VR)devices (such as VR headsets, VR goggles, VR glasses, etc.), augmentedreality (AR) devices (such as AR headsets, AR goggles, AR glasses,etc.), a heart rate monitoring devices (e.g., a chest band, a wristband,etc.), wireless and/or Bluetooth headphones, wireless and/or Bluetoothearbuds, wireless and/or Bluetooth microphones, locationindicating/tracking devices (e.g., global positioning satellite (GPS)devices, emergency beacons, satellite phones, etc.), an electronicwristband, etc.

The second electronic device 102 comprises a processor or processors andlogic and/or instructions configured to cause the processor(s) toperform operations, described in more detail in FIGS. 4-6. Referringagain to FIG. 1, in one implementation, the second electronic device 102is an electronic device that is configured to perform functions inaddition to interacting with the wearable device 114, at least infurtherance of a pairing process between the wearable device 114 and thesecond electronic device 102. The pairing process, once completedsuccessfully, establishes a wireless electronic coupling between thesecond electronic device 102 and the wearable device 114 that provides alink for data and information transfer between the second electronicdevice 102 and the wearable device 114.

The second electronic device 102 may be any type of electronic deviceknown in the art, including portable electronics (e.g., a smartphone, alaptop or notebook computer, a tablet computing device, a digitalcamera, a video recorder, etc.) and electronic devices intended toremain static (e.g., a desktop computing device, home media andentertainment devices, gaming consoles, physical media players (e.g.,Blu-Ray, DVD, etc.) streaming devices, smart TVs, etc.).

As shown in FIG. 1, according to one implementation, the secondelectronic device 102 includes a processor 104 or multiple processorselectrically coupled to a configuration service 110, an image capturedevice 106, and a memory 112. The processor(s) 104 may also beelectrically coupled to a microphone 108 in one implementation.

The processor(s) 104 may include any type of processor known in the art.A portion of the memory 112 may be removable from the second electronicdevice 102, while a different portion of the memory 112 may bepermanently integrated into the second electronic device 102 in animplementation. In some implementations, the memory 112 may comprise anytype of memory and/or storage technologies known in the art.

The image capture device 106 is configured to obtain an image of realworld objects and/or actions, and provide the image to the processor(s)104 for analysis thereof, as described in more detail in FIGS. 4-6.Referring again to FIG. 1, the image capture device 106 may provide astill image, a set of still images, and/or a video that includesmultiple images. The image capture device 106 may comprise a digitalcamera and/or a digital video recorder, and may be complimented by aflash or other light source for providing additional or different typesof light to an object being photographed and/or recorded. The imagecapture device 106 provides the image(s) and/or video(s) in a formatknown in the art and recognizable by the processor(s) 104, such as .jpg,.png, .tiff, .bmp, .sgi, .rgb, .mpeg, .avi, QuickTime, etc.

The microphone 108, when included in the second electronic device 102,is configured to provide audio content to the processor(s) 104. Theaudio content may be captured from a user of the second electronicdevice 102, particularly in furtherance of a pairing process between thesecond electronic device 102 and the wearable device 114. Some exampleaudio content includes, but is not limited to, instructions from theuser to begin, end, and/or proceed to a next step of the pairingprocess, an answer by the user to a query generated during the pairingprocess to provide necessary information for the pairing process,ambient noise present during the pairing process, specific cues and/orsignals generated by the wearable device during the pairing process,etc.

In one approach, one or more sensors of the second electronic device 102may gather information about the second electronic device 102 and/or thewearable device 114. Some example sensors include a temperature monitorconfigured to obtain temperature readings of an object and/or asurrounding environment (e.g., air), an infrared (IR) camera or sensorconfigured to capture IR images of an object or surroundings, aheartrate (HR) monitor configured to obtain a heartrate of user, amotion sensor configured to capture movement of the second electronicdevice 102, etc.

According to an approach, one or more sensors of the wearable device 114may gather information about the wearable device 114. Any of thepreviously described sensors may be included with the wearable device114, along with other sensors known in the art. The sensor informationobtained from sensor(s) of the second electronic device 102 and/or thewearable device 114 may be used alone or in conjunction with informationobtained from the image(s) and/or video(s) provided by the image capturedevice 106.

The configuration service 110, in one implementation, providesinstructions and logic for configuring the wearable device 114 inresponse to receiving the image(s) and/or video(s) from the imagecapture device 106. This process is described in more detail in FIGS.4-6. In addition, with reference to FIG. 1, the second electronic device102 may be provided without the configuration service 110 inimplementations where the wearable device 114 is configured to configureitself (via the configuration service 116 thereon) without the aid ofthe second electronic device 102, except for the provision of thecaptured image(s) and/or video(s).

The processor(s) 104 and/or the configuration service 110, whenimplemented on the second electronic device 102, may analyze theimage(s) and/or video(s) received from the image capture device 106 todetermine aspects of the wearable device 114, as described in moredetail in FIGS. 4-6.

Moreover, referring again to FIG. 1, the second electronic device 102 isconfigured to send and/or receive configuration information 120 toand/or from the wearable device 114 in one implementation. In animplementation, a network 122 may be utilized for transmittingconfiguration information 120 to the wearable device 114, as would beunderstood by one of skill in the art. Any type of network known in theart, including proprietary networks and transmission protocols, may beused for the network 122.

In one implementation, a configuration server 124 may be electricallycoupled to the network 122, and this configuration server 124 mayprovide configuration services for the wearable device 114, particularlyin relation to a pairing process between the wearable device 114 and thesecond electronic device 102.

According to an implementation, the second electronic device 102 mayprovide the configuration information 118 directly to the wearabledevice 114, via an electrical link therebetween.

The wearable device 114 may include, in some implementations, aconfiguration service 116 for analyzing the image(s) and/or video(s)received in the configuration information 118 from the second electronicdevice 102 (and/or the configuration information 120 received via thenetwork 122) to determine aspects of the wearable device 114, asdescribed in more detail in FIGS. 4-6.

With reference to FIG. 1, the configuration information 118 and/or 120may include any information that would be helpful for completing apairing process between the wearable device 114 and the secondelectronic device 102 and/or information that would enable the wearabledevice 114 to perform better or with less input from the user, such as anetwork and/or media access control (MAC) address of an electricaldevice, a name of an electrical device, a serial number and/or anotherunique identifier of an electrical device, an image captured by thesecond electronic device 102 of the wearable device 114, an imagecaptured by the second electronic device 102 of conditions in which thewearable device 114 is being utilized and/or worn, a video captured bythe second electronic device 102 of the wearable device 114, a videocaptured by the second electronic device 102 of conditions in which thewearable device 114 is being utilized and/or worn, an image of agraphical code that represents configuration information of the wearabledevice, etc.

The configuration information 118 and/or 120 may be used to configurethe wearable device 114, at least initially, with little or no inputfrom the user being utilized in the configuration. This configurationmay be possible by providing information about the wearable device 114,such as model, type, size, description, operating system, setuprequirements, position of the wearable device 114 on the body of theuser, orientation of the wearable device 114 relative to other landmarkfeatures such as a body part of the user (e.g., face, wrist, hand, leg,neck, eyes, etc.), clothing, accessories, etc., obtained via analysis ofthe image(s) and/or video(s).

In one implementation, analysis of the image(s) and/or video(s) mayinclude detection of a particular graphical code, pattern, signal, etc.,of a type known in the art, that is presented on a display of thewearable device 114 during the pairing process, such as a bar code,two-dimensional code, quick response (QR) code, decryptable image, etc.

This graphical code may have information embedded therein that isextractable during the analysis, with the information being useful forconfiguration of the wearable device 114, as described in more detailherein.

As shown in FIG. 2, a process 200 for capturing image(s) and/or video(s)of a wearable device 114 is shown in one implementation. A secondelectronic device 102 (shown as a smartphone, but not so limited) may beused to capture the image(s) and/or video(s) of the wearable device 114(shown as an smartwatch, but not so limited) that may be used to provideenhanced configuration features that may be triggered in a pairingprocess (such as pairing the wearable device 114 to the secondelectronic device 102). These image(s) and/or video(s) may be sent tothe wearable device 114 (and/or a configuration server that providesremote configuration service for the wearable device 114) to be analyzedto provide information useful in configuring the wearable device 114 inthe pairing process with the second electronic device 102 and after thepairing process.

Moreover, a graphical code 206 may be output to a display 202 of thewearable device 114 in anticipation of the image(s) and/or video(s)being captured, and the second electronic device 102 may capture animage and/or video of the wearable device 114 displaying the graphicalcode 206, thereby allowing the graphical code 206 to be analyzed inaddition to the image(s) and/or video(s). The graphical code 206 mayinclude indications of aspects of the wearable device 114,characteristics of the user of the wearable device 114, an environmentin which the wearable device is being used, a relationship or conditionsof the wearable device 114 and the user thereof, etc., that arerepresented in a manner understandable by a configuration service uponanalyzing the graphical code 206. During the analysis of the image(s)and/or video(s), upon detection of such a graphical code 206, theconfiguration service will determine the aspects of the wearable device114 (and any other useful information) that have been indicated by thegraphical code 206.

In addition, more than one image and/or video may be captured of thewearable device 114 from more than one angle that may show more or lessdetail of surrounding features in addition to the wearable device 114itself. Some example information that may be obtained from multipleimages and/or video include depth information that further describesdistances between objects shown, infrared (IR) image information,heat/temperature information, etc. Image 208 shows a left hand of theuser with the wearable device 114 being attached to a left wrist, withthe wearable device 114 having a physical input element 204 (thephysical input element 204 is a crown as known in the field of watchesin FIG. 2, but not so limited) on a right side thereof and displaying agraphical code 206. Image 210 shows a close-up view of a front view ofthe wearable device 114, but little detail about the user or othersurrounding details is present in image 210. However, even more clearlyvisible in image 210 is the physical input element 204 positioned on theright side of the wearable device 114, and the graphical code 206displayed by the wearable device 114, which allows for accurate analysisof the graphical code 206 and determination of a physical orientation ofthe physical input element 204.

A wearable device 114 may include any number of physical input elements204, such as a crown, a button (as shown below the crown in images 208and 210), a toggle, a switch, a dial, etc. The physical orientation ofeach of these physical input elements 204 may be captured in theimage(s) and/or video(s), thereby allowing for determination of anorientation of the wearable device 114 based on a predefinedunderstanding of the physical layout of the wearable device 114.

Also, any number of graphical codes 206 (including the absence of a codebeing displayed on the wearable device 114) may be displayedsimultaneously, randomly, or in a predetermined sequence on the display202 of the wearable device 114. In this implementation, each graphicalcode 206 may be configured to provide different, but possiblyoverlapping, information about the wearable device 114, an environmentin which the wearable device 114 is being used, a user, etc. Upondetection of each graphical code 206 of the series of codes, theconfiguration service may determine and assemble portions informationabout the wearable device 114 into a collection of configurationinformation that is provided by the various graphical codes 206.

In an implementation, a moving graphical code 206 may be provided to adisplay of the wearable device 114, in which a video may be used tocapture the movements and/or changes that the graphical code 206undergoes over a certain amount of time (with the movements and/orchanges repeating after the amount of time) or a series of still imagesmay be captured to obtain each the condition of the moving graphicalcode 206 after each movement thereof. These movements and/or changes maybe used to indicate different portions of the configuration information,that is available to be determined from the video and/or images thatcaptures the movements and/or changes, as would be understood by one ofskill in the art upon reading the present descriptions.

According to one implementation, a graphical code 206 may be segmentedinto two or more discrete portions, with each portion representing adifferent aspect of the wearable device 114, a user of the wearabledevice 114, and/or context between the user and the wearable device 114.Each of these segments of the graphical code 206 may be analyzedseparately to determine the discrete information provided by theindividual segment. For example, a QR code may be split into fourportions, with a first portion representing aspects of the user, asecond portion indicating aspects of the wearable device 114, a thirdportion representing an orientation of the wearable device 114 inrelation to the user, and a fourth portion representing identifyinginformation for the various devices. Of course, any segmentation may beprovided in the graphical code 206 as would be understood by one ofskill in the art upon reading the present descriptions.

In an implementation, the graphical code 206 may be an optical label.The optical label may be a machine readable code, a one or twodimensional information symbol, a data matrix code, etc. in accordancewith one implementation, the optical label may be color coded and outputon a display of the wearable device 114 in such a way that the opticallabel is not perceptible to a user when displayed. More specifically,when the optical label is output on the display of the wearable device114, the optical label may be color encoded. In one example, the opticallabel may be displayed in alternating frames, with different colorsbeing encoded in each frame.

In capturing more than the wearable device 114 itself in the image(s)and/or video(s), additional information may be determined from theimage(s) and/or video(s), such as a body part of the user, lightnessand/or darkness of the surroundings, characteristics of the user (skintone, presence of prosthetic(s), left or right hand, arm, or leg wearingthe wearable device 114, etc.). Some or all of this additionalinformation may be included in the aspects of the wearable device 114 asconfiguration information.

Moreover, the presence of the wearable device 114 on a designated bodypart of the user or off the designated body part (e.g., a watch isintended to be worn on a wrist, not an ankle, neck, or held in the hand,etc.) may be used to enable and/or disable certain features of thewearable device 114 in response to detection of the presence of thewearable device 114 in a proper or improper context. For example, somedevices provide unlocking services for itself and/or other paired orrecognized devices in response to a wearable device being worn.Therefore, in response to detection that the wearable device 114 is notbeing worn by the user after analyzing the image(s) and/or video(s),such functionality may be disabled for the wearable device 114 and anyother devices seeking permission to remain unlocked until such time thatthe wearable device 114 is being worn.

According to one implementation, some devices unlock and/or authorizecertain sensitive features (such as payment features, setup services,personal information disclosure, etc.) without requiring determinationof the identity of the user in response to the user unlocking thewearable device initially and the wearable device being constantly wornby the user. In this case, the user will not be required to re-entercredential information to unlock the features each time they areaccessed when the wearable device has constantly been worn since beingunlocked initially. For such functionality to be enabled, the user willbe prompted to enable the functionality prior to the sensitive featuresbeing unlocked automatically based on the wearable device beingconstantly worn by the user.

In an implementation, the captured image(s) and/or video(s) may bedisplayed to the user, such as on a display of the wearable device 114,a display of the second electronic device 102, etc., prior to beinganalyzed, to provide the user an opportunity to review the image(s)and/or video(s) to determine whether a good likeness of the wearabledevice 114 and/or surroundings thereof have been captured. A result ofthis review may lead to the image(s) and/or video(s) being analyzed, oradditional images and/or videos being requested and subsequentlycaptured using the second electronic device 102.

Any suitable GUI may be used on the second electronic device 102 tofacilitate the capturing of the image(s) and/or video(s) as would beunderstood by one of skill in the art upon reading the presentdescriptions. For example, the GUI may prompt the user to take image(s)and/or video(s) of the wearable device 114 from a predetermined set ofangles, then analyze the captured image and/or video to determinewhether the requested operation was performed. When the requestedoperation is performed, a next prompt may be presented for an operationto be performed (e.g., an image or video from a different angle, of adifferent portion of the wearable device 114, etc.). After a sufficientnumber of images and/or videos have been captured, the second electronicdevice 102 may send the image(s) and/or video(s) as configurationinformation to the wearable device 114 and the GUI may indicatecompletion of this part of the pairing process.

In addition, any suitable GUI may be used on the wearable device 114 tofacilitate the capturing of the image(s) and/or video(s) as would beunderstood by one of skill in the art upon reading the presentdescriptions. For example, the GUI may display the graphical code(s) 206and prompt the user to indicate when a code from the series has beencaptured, or display the series of codes or moving code in a repeatingloop. In one implementation, no specific GUI for the pairing process maybe displayed on the wearable device 114, in which a majority of theconfiguration activity is performed by the second electronic device 102and/or a configuration server remote from the wearable device 114.

Now referring to FIG. 3, four orientations of a wrist-worn wearabledevice (e.g., a smartwatch) 316 are shown in various implementations. Ineach orientation, a position of a physical input element (e.g., a crown)306 on the smartwatch 316 and a left or right hand (or wrist dependingon how it is described) on which the smartwatch 316 is being worn areused as descriptions for the particular orientation. In orientation 308,the smartwatch 316 is worn on the left hand 302 with the crown 306 beingpositioned on a right side of the smartwatch 316, which may be indicatedas “LR.” In orientation 310, the smartwatch 316 is worn on the left hand302 with the crown 306 being positioned on a left side of the smartwatch316, which may be indicated as “LL.” In orientation 312, the smartwatch316 is worn on the right hand 304 with the crown 306 being positioned ona right side of the smartwatch 316, which may be indicated as “RR.” Inorientation 314, the smartwatch 316 is worn on the right hand 304 withthe crown 306 being positioned on a left side of the smartwatch 316,which may be indicated as “RL.”

The configuration information may include details about one of theseorientations that are determined from the image(s) and/or video(s)captured for analysis in the pairing process. Of course, any other typeof wearable device known in the art may have similar orientationsspecific to the particular wearable, and these specific orientations maybe determined from the image(s) and/or video(s) used in determining theconfiguration information for the particular wearable in the pairingprocess, so that an orientation of the wearable is known forconfiguration of the wearable device in the pairing process.

In one implementation, a wearable device, e.g., the smartwatch 316 asshown in FIG. 3, may be held by the user rather than being coupled to anappropriate body part, clothing item, etc., e.g., the wrist for asmartwatch 316. In one such implementation, the smartwatch 316 may beheld in the user's palm or hand. However, even while being uncoupledfrom the user and/or positioned at an unusual location on the user'sbody (e.g., not the wrist), the orientation of the smartwatch 316 withrespect to the user may be determined, along with the orientation of anyphysical input elements thereof, such as the crown 306, with respect tothe smartwatch 316.

Further, upon detection that the smartwatch 316 is positioned unusuallybased on a first image, the user may be alerted or prompted to properlyorient and/or position the smartwatch 316 on a wrist, and then tocapture a second image of the smartwatch 316 after it is repositioned,so that the second image depicts how the smartwatch 316 will be operatedby the user.

This type of alert system may be implemented with any wearable devicewith the knowledge of where the wearable device is typically positionedin order to be utilized by a user. After analyzing a first image thatshows that the wearable device as depicted in the first image deviatesfrom the typical position, the user may be alerted as to where a moreappropriate position exists for the wearable device, and the user may befurther implored to position the wearable device in accordance with thisinformation and then to capture a second image to verify that thewearable device has been repositioned properly.

Example Processes

To enable the reader to obtain a clear understanding of thetechnological concepts described herein, the following processesdescribe specific steps performed in a specific order. However, one ormore of the steps of a particular process may be rearranged and/oromitted while remaining within the contemplated scope of the technologydisclosed herein. Moreover, different processes, and/or steps thereof,may be combined, recombined, rearranged, omitted, and/or executed inparallel to create different process flows that are also within thecontemplated scope of the technology disclosed herein. Additionally,while the processes below may omit or briefly summarize some of thedetails of the technologies disclosed herein for clarity, the detailsdescribed in the paragraphs above may be combined with the process stepsdescribed below to get a more complete and comprehensive understandingof these processes and the technologies disclosed herein.

FIG. 4 is flow diagram of an example method 400 for utilizing capturedimages to configure a wearable device. For example, method 400 may beperformed by a wearable device 114, a second electronic device 102, aconfiguration server 124, or some combination thereof, as described inFIG. 1. Moreover, in the descriptions of FIG. 4, the computing devicemay be any suitable computing device known in the art, such as awearable device, a second electronic device separate from the wearabledevice, a configuration server remote from the wearable device and thesecond electronic device, etc.

In step 402, indication that a wearable device has started a pairingprocess with a second electronic device is received. In oneimplementation, the indication may be in the form of an electronicmessage, alert, request, notice, communication, or some other known typeof electronic correspondence, sent from an electronic device, such asthe second electronic device and/or the wearable device.

In an implementation, the indication may be determined by monitoringactions and/or communications to/from the wearable device and/or thesecond electronic device, in which case activity that is indicative of apairing process being started may be determined.

In one approach, a pairing process is not needed prior to obtainingimages of the wearable device, as any triggering event may be used tocause the images to be obtained so that configuration information may bedetermined from the images. In one approach, a triggering event may be arequest from the user to start the configuration

In one example, no triggering event is required before the images areobtained.

At step 404, images corresponding to the wearable device are obtained.The images may be in the form of pictures, video, or some other suitableimage format known in the art that is capable of being analyzed fordetermining content thereof.

In one implementation, the images are captured by the second electronicdevice using a camera and/or video recorder thereof. Moreover, a lightsource may be utilized to enhance the wearable device and/or to reveal aparticular aspect of the wearable device not recognizable without use ofthe light source, such as IR reactive text or images on a display orexterior of the wearable device, black light reactive text or images ona display or exterior of the wearable device, etc.

In step 406, the images are analyzed to determine aspects of thewearable device. This analysis may be performed by a machine learningmodule or a group of machine learning modules, which may be present onthe wearable device, on the second electronic device, and/or on theconfiguration server. The analysis may utilize any image manipulationand detection techniques known in the art, including but not limited to,pattern recognition, digital geometric analysis, signal processing,image segmentation, motion detection, video tracking, optical flowanalysis, object-based image analysis, etc.

The aspects that are determined from the images may represent anycharacteristic, condition, form, trait, capability, feature, and/orattribute of the wearable device, surroundings of the wearable device,and/or a user of the wearable device as captured in the images.

In one example, the aspects of the wearable device may include, but arenot limited to, a manufacturer and model of the wearable device, a sizeof the wearable device, a tightness of a band of the wearable device ona body part of a user, a position of the wearable device on the user, anorientation of the wearable device with respect to itself and the user,a material of the wearable device, a material of the band of thewearable device, a color of the wearable device, a color of the band ofthe wearable device, a graphical code displayed on the wearable device,etc.

In an implementation, the aspects of the wearable device may include anorientation of a physical input element of the wearable device withrespect to a body of the wearable device, e.g., where a crown or buttonis positioned with respect to a display of the wearable device and onwhich side of the wearable device the crown or button is positioned(left or right side). The orientation of the physical input element maybe used to determine how input received from the physical input elementis transformed into an operation by the wearable device.

For example, a crown which spins clockwise and counter-clockwise maycause displayed information to scroll up or down (a scrollingdirection), depending on which direction the crown is rotated. From thepoint of view of the user, rotation in one direction may be anticipatedto cause scrolling up, but the orientation of the wearable device (onwhich side the crown is located) may cause an action that is reversed tothis perception, and the displayed information may scroll down as aresult of the rotational input. Therefore, the wearable device isconfigured to cause a toggle and/or scrolling direction (which directionto move content on a display of the wearable device) for display torespond in an anticipated way to rotational input (e.g., when the crownis on the right side, clockwise scrolls up and counter-clockwise scrollsdown; when the crown is on the left side, clockwise scrolls down andcounter-clockwise scrolls up in response to activation of the crown. Ofcourse, these directions and rotational inputs are for example, andother combinations are possible based on a user's desire and defaultsettings of the wearable device.

In one implementation, the image(s) corresponding to the wearable deviceinclude an image of the wearable device positioned on a body part of auser, such as a hand or wrist of the user for a watch or wristband, afinger of the user for a fitness tracking ring, a face of the user forAR/VR glasses or goggles, etc.

In an example, a physical orientation of the wearable device withrespect to a body part of the user on which the wearable device iscoupled to the user may be determined by analysis of the images, e.g.,which wrist a watch is being worn on and an orientation of the watchwith respect to the hand of the user, e.g., LL, LR, RL, RR, which fingera ring is being worn on, how tightly a watchband is closed around awrist, where on the wrist the watch is being worn (adjacent to the hand,farther from the hand behind the wrist bone, etc.), how tightly a cheststrap is closed around a user's chest, etc.

At step 408, the wearable device is configured using the aspects of thewearable device. This configuration may take place in addition to or aspart of the pairing process.

In one implementation, the wearable device is a smartwatch and the bodypart is a wrist or hand of the user. In this implementation, the aspectsof the wearable device include a determination of which wrist of theuser the smartwatch is being worn on, a determination of whether thesmartwatch is positioned on an inside or an outside of the wrist of theuser (the inside of the wrist is closest to the palm of the hand, withthe outside being opposite the inside), and a determination of anorientation of a crown of the smartwatch, e.g., RL, LR, RR, LL.

The aspects may be used to configure how navigational directions areprovided by the wearable device based on an orientation of the wearabledevice on a body of the user, how motion is indicated by the wearabledevice based on an orientation of the wearable device with respect tothe user's viewing angle (up versus down, left versus right, etc.), howthe wearable device is indicated on a display of the wearable device(color, size, model, etc.), etc.

For example, for a smartwatch positioned on a left wrist of the user, aforward indicated navigational cue may appear as an up arrow on thedisplay of the wearable device when the elbow is bent about 90° forviewing of the display of the smartwatch. Moreover, a right navigationalcue may appear as an arrow pointing toward the left hand of the user anda left navigational cue may appear as an arrow pointing up the left armof the user.

In contrast, for a smartwatch worn on the right hand of the user, thenavigational cues may be adjusted to account for the placement andorientation of the smartwatch. For example, should the face of the watchbe flipped 180° in comparison with how it was worn on the left hand,then a forward navigational cue arrow may also be flipped, sincedisplaying the arrow as configured for left-hand wearing would result inthe arrow pointing back at the user, not forward away from the user.Moreover, the left and right navigational cues may also be configured tobe reversed as a result of the smartwatch being worn on the right handof the user instead of the left hand (and the watch face flipped 180°).

In an implementation, the aspects of the wearable device that aredetermined as a result of the analysis are each assigned a confidencescore subsequent to determination of the aspects of the wearable device.These confidence scores may be based on any known algorithms and/ormethodologies for creation of and usage of confidence scores as areknown in the art.

Moreover, after calculation of the confidence scores for each aspect, arequest to confirm a first aspect may be displayed to the computingdevice in response to a corresponding confidence score assigned to thefirst aspect being less than a predetermined threshold, e.g., 50%, 60%,75%, 80%, etc. Thereafter, the wearable device is configured inaccordance with the first aspect in response to receiving confirmationof the first aspect indicated by the request.

In an implementation, the wearable device is configured in accordancewith a second aspect in response to a determination that a correspondingconfidence score assigned to the second aspect is at least equal to thepredetermined threshold, e.g., 50%, 60%, 75%, 80%, etc., withoututilizing a request to confirm the second aspect.

Further, one aspect that is determined about the wearable device that isin conflict with another aspect (e.g., both aspects are not possible toexist at the same time) are refined based on their correspondingconfidence scores to narrow down the results for the user. For example,if the analysis determines there is a 20% confidence that the wearabledevice is positioned on a right hand, and a 80% confidence that thewearable is positioned on a left hand, only the aspect that indicatesthat the wearable device is positioned on the left hand is provided tothe configuration service for configuring the wearable device.

Moreover, for undetermined aspects, e.g., 50/50 confidence scores or nomajority results from multiple conflicting aspects, e.g., 33/33/33confidence scores for conflicting aspects, a request to choose whichaspect is correct may be presented to the user, on a display of one ofthe devices. Upon selection of which aspect is correct, this selectedaspect will be provided for configuration of the wearable device.

The method 400 may also include determining that the physicalorientation of the wearable device is not optimized for the user basedon the aspects resulting from the analysis. Thereafter, the user may bealerted to the non-optimized physical orientation of the wearabledevice, such as via an indication being displayed on one of the devices,an audible alert or audio file being output by one of the devices,haptic feedback that provides vibrational output to the user, etc. Whenpossible, a notification is provided with an alert that describes acorrection to the physical orientation of the wearable device for theuser to implement.

For example, if it is determined that a wristband is being worn tooloosely to properly detect health data, such as a heartrate, glucose,etc., of the user, a message may be displayed on the wristbandindicating to tighten the wristband. In a further approach, the user maybe asked to capture a follow-up image after adjusting the wearabledevice to review the changes and ensure that the positioning andcoupling to the user is adjusted properly. If not, follow-upinstructions may be presented to the user via any electronic deviceavailable.

In an example, if a watch is being worn too high on the wrist of theuser (too far away from the hand), the user may be alerted to thecondition, such as by displaying a message on the second electronicdevice during the pairing process or thereafter, to move the watchcloser to the hand to provide better contact with the user's wrist forcertain sensors of the watch, such as a heartrate monitor, anelectrocardiogram (EKG or ECG) sensor, a temperature sensor, etc.

In one implementation, in response to detection of an object near to thewearable device that may obstruct normal or optimal performance of thewearable device and/or sensors of the wearable device, the user may bealerted to correct, minimize, or remove the obstruction. This alert maybe provided visually, audibly, and/or haptically via the wearabledevice, the second electronic device, or a suitable device.

For example, a bracelet for a smartwatch may be an obstruction becauseit may slide between the smartwatch and the wrist of the user and reduceor obstruct a heartrate monitor from determining a heartrate of theuser. Also, a necklace for a chest strap may be an obstruction becauseit may slide between the chest strap and the chest of the user andprevent the monitor from determining the heartrate of the user. Inaddition, earrings for wireless headphones may be an obstruction becausethey may push the headphones away from the ear and limit the maximumvolume and/or make wearing of the headphones uncomfortable.

According to one approach, a captured image may show that a skincondition exists that may affect performance of the wearable device, andthe wearable device may be configured to account for the presence of thecondition in any suitable way. In one approach, the user may be promptedto determine whether the user desires to have the wearable device takeinto consideration the skin condition prior to any action being taken bythe wearable device to account for the presence of the condition in asuitable way. In one example, a tattoo may be positioned on skin of theuser where a wearable device's sensors are located for reading acharacteristic of the user, such as a temperature or heartrate. In thiscase, the wearable device may adjust sensor power to be stronger and/oradjust sensor thresholds to be lower in order to account for thepresence of the tattoo, which may cause readings to be more difficult toobtain through the tattooed skin using the wearable device's sensor(s),such as a heartrate sensor, ECG sensor, temperature sensor, perspirationsensor, IR light sensor, etc.

According to an approach, an image may indicate characteristics of auser's body (e.g., vein appearance, skin thickness, wrinkles, skincoloration, age spots, scars, bruises, mole presence, amount of hair,etc. In response to detection of the user's characteristics, the displayof the wearable device may be adjusted accordingly. In one approach, theuser may be prompted to determine whether the user desires to have thewearable device take into consideration the perceived age of the userand/or to verify the perceived age of the user prior to any action beingtaken by the wearable device to account for the user's age.

In an example, based on a determination that a user is within a certainage range that may benefit from alterations to the wearable device, thewearable device may be configured for use by a person within an agerange who may have trouble reading small print by enlarging the textsize on a screen of the device and/or increasing a size of buttonsdisplayed on a touchscreen of the device to allow for more imprecisetouch inputs to still trigger a desired function or action. Further, thewearable device may have a volume for audio settings set louder, as manypeople have trouble hearing and louder volume settings may help the userto hear any audio alerts, instructions, directions, etc., produced bythe wearable device.

In one example, based on a determination that a user is younger, thewearable device may be placed into a kid-friendly mode or a simple mode,that is configured to restrict some content availability to the user(complicated content may be restricted and/or age-appropriate contentmay only be provided). Further, the wearable device may be configured tooperate with a simplified interface for the user to enable a youngeruser to more easily understand the functionality available.

In an example, the image may show that a sensor of the wearable deviceis not positioned in an optimal location or range of positions on thebody of the user. In this case, the user may be alerted to adjust aposition and/or orientation of the wearable device to position in whicha sensor of the wearable device is better positioned to provide strongerreadings taken from the body of the user. This alert may be producedaudibly, visually, and/or haptically via the wearable device, the secondelectronic device, or some other suitable device.

In one example, a wearable device may comprise a glucose meter orsensor, and this glucose meter may operate better on the left wrist ofthe user. In response to the image indicating that the wearable deviceis positioned on the right wrist of the user, the user may be alerted toswitch the wearable device to the left wrist in order to provide betterglucose readings.

According to one approach, the image may show that the wearable deviceis oriented or positioned in a certain way (rotated relative to itselfand/or moved relative to the user). By determining the orientation orposition of the wearable device, features, interface(s), and/or feedbackfrom the wearable device may be adjusted to account for the detectedorientation or position. In one implementation, motion of the wearabledevice as a result of the user moving a body part may cause the wearabledevice to perform a function, e.g., wake, sleep, begin trackingactivity, play media content, etc. In order for the wearable device toproperly respond to the user's motion, the wearable device is configuredto account for the position of the wearable device on the user based onanalysis of the image such that movements of the wearable device resultin predetermined features of the wearable device to be performed.

For example, a smartwatch may be worn on an inside or outside of a leftor right wrist, which may be determined from the image. In response todetection that a smartwatch is being worn on an inside of a right wrist,motion of the user's hand upward with the smartwatch in this orientationwould be reversed from motion of the user's hand upward with thesmartwatch being worn on the outside of the right wrist. Therefore, thesmartwatch is configured to account for how motion is perceived and isbased on the location of the smartwatch on the body of the user, andorientation of the smartwatch relative to itself, that is determinedfrom analysis of the image.

According to one approach, for a wearable device that includes adisplay, the orientation of a user interface (UI) provided on thedisplay may be adjusted based on a position and/or orientation of thewearable device on the body of the user. For example, for a smartwatch,the orientation of the UI will be reversed (flipped upside down 180°)for a smartwatch being worn on the left hand versus on the right hand,when the body of the smartwatch is oriented to have the same side of thesmartwatch be closer to the hand. Similarly, the orientation of the UIis reversed for a smartwatch being worn on the inside of the wristversus the outside of the wrist, given that the same side of thesmartwatch is closest to the hand. These UI orientations may beconfigured on the wearable device based on the analysis of the image todetermine the position and/or orientation of the wearable device withrespect to the body of the user.

The wearable device may have different features associated withdifferent movements of the wearable device, and therefore determininghow the wearable device is positioned on the body of the user is helpfulfor configuration of the wearable device. For a case where the wearabledevice is worn on a user's wrist, and upward movement wakes the deviceup for ease of use (so that the user does not have to manually wake thedevice up to use it), while the wrist and hand being in a loweredposition puts the device to sleep to conserve battery, which hand and onwhich side of the wrist the wearable device is coupled to the user isstored as configuration information that is used to configure thewearable device to understand which movement causes the device to wake,and which movement causes the device to sleep.

In all of the above described processes and procedures, the data that iscollected by the wearable device is stored on the wearable device, andis not uploaded to a server or device that aggregates such information.Moreover, any data that is transferred from the wearable device to thesecond electronic device is stored on the second electronic device andnot uploaded to a server or aggregation device. Moreover, any dataobtained by the second electronic device, such as images of the wearabledevice, or not shared with any other device.

FIG. 5 is flow diagram of an example method 500 for utilizing imagescaptured for a paring process. For example, method 500 may be performedby a wearable device 114, a second electronic device 102, aconfiguration server 124, or some combination thereof, as described inFIG. 1. Moreover, in the descriptions of FIG. 5, method 500 may beperformed by a wearable device to perform a pairing process with asecond electronic device.

In step 502, a paring process is started by the wearable device to pairwith a second electronic device, such as a smartphone, tablet computingdevice, laptop computing device, notebook computing device, mediadevice, etc. The wearable device may be any type of wearable or portableelectronic device known in the art, such as a smartwatch, an electronicwristband, a GPS device, AR/VR glasses or goggles, etc.

The pairing process may be configured to establish a securecommunication channel between the wearable device and the secondelectronic device using any known wireless communication technology,such as Bluetooth, RF, IR, Wi-Fi, Wi-Max, etc.

Details of the full extent of the pairing process are omitted here, butmay be performed in accordance with other known pairing processes, withthe caveat that configuration information used in the pairing processand/or for configuration of the wearable device after the pairingprocess may be determined from images collected of the wearable device,as described herein in various implementations.

In step 504, an image that corresponds to the wearable device isreceived by the device which is performing method 500. The image may bea picture, one of several images received, a frame of a video, etc., andmay correspond to the wearable device by including a representation ofthe wearable device and/or surroundings of the wearable device inrelation to a user of the wearable device, as described herein.

In step 506, the image is analyzed to determine aspect(s) of thewearable device. The analysis may be performed in accordance with anyknown techniques for image and/or video analysis as described hereinand/or as known in the art.

The aspect(s) may include, but are not limited to, a manufacturer andmodel of the wearable device, a size of the wearable device, a tightnessof a band of the wearable device on a body part of a user, a material ofthe wearable device, a material of the band of the wearable device, acolor of the wearable device, a color of the band of the wearabledevice, a physical orientation of the wearable device with respect to abody part of the user on which the wearable device is coupled to theuser, an orientation of a physical input element of the wearable devicewith respect to a body of the wearable device, etc.

In step 508, the pairing process is completed between the wearabledevice and the second electronic device using the aspect(s) in anycapacity that they are helpful in the pairing process.

For example, the model of the wearable device may be used in the pairingprocess to access instructions that are specific to that particularmodel of wearable device and use those specific instructions to completethe pairing process without requiring input from the user to specify thewearable device's model.

In an example, a shape, size, type, color and/or material of thewearable device, a band thereof, or any other physical aspect of thewearable device may be used to visually represent the wearable device ona display of the second electronic device. In this example, the user mayselect the visual representation of the wearable device prior toutilizing the wearable device in conjunction with the second electronicdevice, in a fashion that is easier than remembering a unique identifierof the wearable device, name, etc., that are displayed in a list.

FIG. 6 is flow diagram of an example method 600 for utilizing imagescaptured for a configuration process. For example, method 600 may beperformed by a wearable device 114, a second electronic device 102, aconfiguration server 124, or some combination thereof, as described inFIG. 1.

Referring again to FIG. 6, in step 602, an image that corresponds with awearable device is received. In one implementation, several imagesand/or a video that corresponds with the wearable device may bereceived. In one approach, the image(s) may be captured by the secondelectronic device using a camera and/or video recorder thereof. Thesecond electronic device may be any type of device known in the art,such as a smartphone, tablet computing device, laptop computing device,notebook computing device, media device, etc. The wearable device may beany type of wearable or portable electronic device known in the art,such as a smartwatch, an electronic wristband, a GPS device, AR/VRglasses or goggles, etc.

The images may be pictures, video, etc., and may correspond to thewearable device by including images of the wearable device and/orsurroundings of the wearable device in relation to a user of thewearable device, as described herein.

In step 604, the images are analyzed to determine aspect(s) of thewearable device. The analysis may be performed in accordance with anyknown techniques for image and/or video analysis as described hereinand/or as known in the art.

The aspect(s) may include, but are not limited to, a manufacturer andmodel of the wearable device, a size of the wearable device, a tightnessof a band of the wearable device on a body part of a user, a material ofthe wearable device, a material of the band of the wearable device, acolor of the wearable device, a color of the band of the wearabledevice, a physical orientation of the wearable device with respect to abody part of the user on which the wearable device is coupled to theuser, an orientation of a physical input element of the wearable devicewith respect to a body of the wearable device, etc.

In step 606, the aspect(s) are used to configure the wearable device.The configuration of the wearable device may be performed in accordancewith any known configuration scheme or method, with the caveat that somedetails about the wearable device that may typically be input by a userare instead provided by the analysis of the image(s), such as anorientation of the wearable device with respect to the user, anorientation of physical input elements of the wearable device withrespect to the body of the wearable device, a model of the wearabledevice, a network and/or MAC address of the wearable device, etc.

Graphical User Interfaces

This disclosure above describes various Graphical User Interfaces (GUIs)for implementing various features, processes or workflows. These GUIsmay be presented on a variety of electronic devices including, but notlimited to, laptop computers, notebook computers, desktop computers,computer terminals, television systems, tablet computers, home media andentertainment devices, e-book readers and smart phones. One or more ofthese electronic devices can include a touch-sensitive surface. Thetouch-sensitive surface can process multiple simultaneous points ofinput, including processing data related to the pressure, degree orposition of each point of input. Such processing can facilitate gestureswith multiple fingers, including pinching and swiping.

When the disclosure refers to “select” or “selecting” user interfaceelements in a GUI, these terms are understood to include clicking or“hovering” with a mouse or other input device over a user interfaceelement, or touching, tapping or gesturing with one or more fingers orstylus on a user interface element. User interface elements can bevirtual buttons, menus, selectors, switches, sliders, scrubbers, knobs,thumbnails, links, icons, radio buttons, checkboxes and any othermechanism for receiving input from, or providing feedback to a user.

Privacy

As described above, one aspect of the present technology is thegathering and use of data available from specific and legitimate sourcesto provide enhanced features in a pairing process. The presentdisclosure contemplates that in some instances, this gathered data mayinclude personal information data that uniquely identifies or can beused to identify a specific person. Such personal information data caninclude demographic data, location-based data, online identifiers,telephone numbers, email addresses, twitter ID's, home addresses, dataor records relating to a user's health or level of fitness (e.g., vitalsigns measurements, medication information, exercise information), dateof birth, or any other identifying or personal information.

The present disclosure recognizes that the use of such personalinformation data, in the present technology, can be used to the benefitof users. For example, the personal information data can be used toconfigure a wearable device in a more user friendly manner than iscurrently possible. Accordingly, use of such personal information dataenables users to enjoy benefits of the wearable device withoutundergoing a rigorous pairing process and subsequent configurationprocess. Further, other uses for personal information data that benefitthe user are also contemplated by the present disclosure. For instance,health and fitness data may be used, in accordance with the user'spreferences, to provide insights into their general wellness, or may beused as positive feedback to individuals using technology to pursuewellness goals.

The present disclosure contemplates that those entities responsible forthe collection, analysis, disclosure, transfer, storage, or other use ofsuch personal information data will comply with well-established privacypolicies and/or privacy practices. In particular, such entities would beexpected to implement and consistently apply privacy policies andpractices that are generally recognized as meeting or exceeding industryor governmental requirements for maintaining the privacy of users. Suchinformation regarding the use of personal data should be prominently andeasily accessible by users, and should be updated as the collectionand/or use of data changes. Personal information from users should becollected for legitimate and reasonable uses of the entity and notshared or sold outside of those legitimate uses only. Further, suchcollection/sharing should occur only after receiving the informedconsent of the users or other legitimate basis specified in applicablelaw. Additionally, such entities should consider taking any needed stepsfor safeguarding and securing access to such personal information dataand ensuring that others with access to the personal information dataadhere to their privacy policies and procedures. Further, such entitiescan subject themselves to evaluation by third parties to certify theiradherence to widely accepted privacy policies and practices. Inaddition, policies and practices should be adapted for the particulartypes of personal information data being collected and/or accessed andadapted to applicable laws and standards, includingjurisdiction-specific considerations which may serve to impose a higherstandard. For instance, in the US, collection of or access to certainhealth data may be governed by federal and/or state laws, such as theHealth Insurance Portability and Accountability Act (HIPAA); whereashealth data in other countries may be subject to other regulations andpolicies and should be handled accordingly.

Despite the foregoing, the present disclosure also contemplatesembodiments in which users selectively block the use of, or access to,personal information data. That is, the present disclosure contemplatesthat hardware and/or software elements can be provided to prevent orblock access to such personal information data. For example, in the caseof a pairing process for a wearable device, the present technology canbe configured to allow users to select to “opt in” or “opt out” ofparticipation in the collection of personal information data duringregistration for services or anytime thereafter. In addition toproviding “opt in” and “opt out” options, the present disclosurecontemplates providing notifications relating to the access or use ofpersonal information. For instance, a user may be notified upondownloading an app that their personal information data will be accessedand then reminded again just before personal information data isaccessed by the app.

Moreover, it is the intent of the present disclosure that personalinformation data should be managed and handled in a way to minimizerisks of unintentional or unauthorized access or use. Risk can beminimized by limiting the collection of data and deleting data once itis no longer needed. In addition, and when applicable, including incertain health related applications, data de-identification can be usedto protect a user's privacy. De-identification may be facilitated, whenappropriate, by removing identifiers, controlling the amount orspecificity of data stored (e.g., collecting location data at a citylevel rather than at an address level), controlling how data is stored(e.g., aggregating data across users), and/or other methods such asdifferential privacy.

Therefore, although the present disclosure broadly covers use ofpersonal information data to implement one or more various disclosedembodiments, the present disclosure also contemplates that the variousembodiments can also be implemented without the need for accessing suchpersonal information data. That is, the various embodiments of thepresent technology are not rendered inoperable due to the lack of all ora portion of such personal information data. For example, content can beselected and delivered to users based on aggregated non-personalinformation data or a bare minimum amount of personal information, suchas the content being handled only on the user's device or othernon-personal information available to the pairing process.

Example System Architecture

FIG. 7 is a block diagram of an example computing device 700 that canimplement the features and processes of FIGS. 1-6. The computing device700 can include a memory interface 702, one or more data processors,image processors and/or central processing units 704, and a peripheralsinterface 706. The memory interface 702, the one or more processors 704and/or the peripherals interface 706 can be separate components or canbe integrated in one or more integrated circuits. The various componentsin the computing device 700 can be coupled by one or more communicationbuses or signal lines.

Sensors, devices, and subsystems can be coupled to the peripheralsinterface 706 to facilitate multiple functionalities. For example, amotion sensor 710, a light sensor 712, and a proximity sensor 714 can becoupled to the peripherals interface 706 to facilitate orientation,lighting, and proximity functions. Other sensors 716 can also beconnected to the peripherals interface 706, such as a global navigationsatellite system (GNSS) (e.g., GPS receiver), a temperature sensor, abiometric sensor, magnetometer or other sensing device, to facilitaterelated functionalities.

A camera subsystem 720 and an optical sensor 722, e.g., a chargedcoupled device (CCD) or a complementary metal-oxide semiconductor (CMOS)optical sensor, can be utilized to facilitate camera functions, such asrecording photographs and video clips. The camera subsystem 720 and theoptical sensor 722 can be used to collect images of a user to be usedduring authentication of a user, e.g., by performing facial recognitionanalysis.

Communication functions can be facilitated through one or more wirelesscommunication subsystems 724, which can include radio frequencyreceivers and transmitters and/or optical (e.g., infrared) receivers andtransmitters. The specific design and implementation of thecommunication subsystem 724 can depend on the communication network(s)over which the computing device 700 is intended to operate. For example,the computing device 700 can include communication subsystems 724designed to operate over a GSM network, a GPRS network, an EDGE network,a Wi-Fi or WiMax network, and a Bluetooth™ network. In particular, thewireless communication subsystems 724 can include hosting protocols suchthat the device 100 can be configured as a base station for otherwireless devices.

An audio subsystem 726 can be coupled to a speaker 728 and a microphone730 to facilitate voice-enabled functions, such as speaker recognition,voice replication, digital recording, and telephony functions. The audiosubsystem 726 can be configured to facilitate processing voice commands,voiceprinting and voice authentication, for example.

The I/O subsystem 740 can include a touch-surface controller 742 and/orother input controller(s) 744. The touch-surface controller 742 can becoupled to a touch surface 746. The touch surface 746 and touch-surfacecontroller 742 can, for example, detect contact and movement or breakthereof using any of a plurality of touch sensitivity technologies,including but not limited to capacitive, resistive, infrared, andsurface acoustic wave technologies, as well as other proximity sensorarrays or other elements for determining one or more points of contactwith the touch surface 746.

The other input controller(s) 744 can be coupled to other input/controldevices 748, such as one or more buttons, rocker switches, thumb-wheel,infrared port, USB port, and/or a pointer device such as a stylus. Theone or more buttons (not shown) can include an up/down button for volumecontrol of the speaker 728 and/or the microphone 730.

In one implementation, a pressing of the button for a first duration candisengage a lock of the touch surface 746; and a pressing of the buttonfor a second duration that is longer than the first duration can turnpower to the computing device 700 on or off. Pressing the button for athird duration can activate a voice control, or voice command, modulethat enables the user to speak commands into the microphone 730 to causethe device to execute the spoken command. The user can customize afunctionality of one or more of the buttons. The touch surface 746 can,for example, also be used to implement virtual or soft buttons and/or akeyboard.

In some implementations, the computing device 700 can present recordedaudio and/or video files, such as MP3, AAC, and MPEG files. In someimplementations, the computing device 700 can include the functionalityof a digital audio, video, and/or media player.

The memory interface 702 can be coupled to memory 750. The memory 750can include high-speed random-access memory and/or non-volatile memory,such as one or more magnetic disk storage devices, one or more opticalstorage devices, and/or flash memory (e.g., NAND, NOR). The memory 750can store an operating system 752, such as Darwin, RTXC, LINUX, UNIX, OSX, WINDOWS, or an embedded operating system such as VxWorks.

The operating system 752 can include instructions for handling basicsystem services and for performing hardware dependent tasks. In someimplementations, the operating system 752 can be a kernel (e.g., UNIXkernel). In some implementations, the operating system 752 can includeinstructions for performing voice authentication. For example, operatingsystem 752 can implement the advanced pairing process features asdescribed with reference to FIGS. 1-6.

The memory 750 can also store communication instructions 754 tofacilitate communicating with one or more additional devices, one ormore computers and/or one or more servers. The memory 750 can includegraphical user interface instructions 756 to facilitate graphic userinterface processing; sensor processing instructions 758 to facilitatesensor-related processing and functions; phone instructions 760 tofacilitate phone-related processes and functions; electronic messaginginstructions 762 to facilitate electronic-messaging related processesand functions; web browsing instructions 764 to facilitate webbrowsing-related processes and functions; media processing instructions766 to facilitate media processing-related processes and functions;GNSS/Navigation instructions 768 to facilitate GNSS andnavigation-related processes and instructions; and/or camerainstructions 770 to facilitate camera-related processes and functions.

The memory 750 can store software instructions 772 to facilitate otherprocesses and functions, such as the advanced pairing processes andfunctions using image capture as described with reference to FIGS. 1-6.

The memory 750 can also store other software instructions 774, such asweb video instructions to facilitate web video-related processes andfunctions; and/or web shopping instructions to facilitate webshopping-related processes and functions. In some implementations, themedia processing instructions 766 are divided into audio processinginstructions and video processing instructions to facilitate audioprocessing-related processes and functions and video processing-relatedprocesses and functions, respectively.

Each of the above identified instructions and applications cancorrespond to a set of instructions for performing one or more functionsdescribed above. These instructions need not be implemented as separatesoftware programs, procedures, or modules. The memory 750 can includeadditional instructions or fewer instructions. Furthermore, variousfunctions of the computing device 700 can be implemented in hardwareand/or in software, including in one or more signal processing and/orapplication specific integrated circuits.

What is claimed is:
 1. A method comprising: receiving, by a computingdevice, one or more images corresponding to a wearable device;analyzing, by the computing device, the one or more images to determineone or more aspects of the wearable device; and configuring, by thecomputing device, the wearable device using the one or more aspects ofthe wearable device.
 2. The method as recited in claim 1, furthercomprising receiving, by the computing device, indication that thewearable device has started a pairing process with a second electronicdevice prior to receiving the one or more images corresponding to thewearable device, wherein the one or more images corresponding to thewearable device include at least one image of the wearable devicepositioned on a body part of a user.
 3. The method as recited in claim2, wherein the wearable device is a smartwatch and the body part is awrist of the user, and wherein the one or more aspects of the wearabledevice are selected from a group consisting of: a determination of whichwrist of the user the smartwatch is being worn on, a determination ofwhether the smartwatch is positioned on an inside or an outside of thewrist of the user, and a determination of an orientation of a crown ofthe smartwatch.
 4. The method as recited in claim 1, wherein the one ormore aspects of the wearable device comprise an orientation of aphysical input element of the wearable device with respect to a body ofthe wearable device.
 5. The method as recited in claim 1, wherein theanalyzing the one or more images to determine the one or more aspects ofthe wearable device comprises assigning a confidence score to each ofthe one or more aspects of the wearable device subsequent todetermination of the one or more aspects of the wearable device.
 6. Themethod as recited in claim 5, further comprising: causing display, bythe computing device, of a request to confirm a first aspect of the oneor more aspects in response to a corresponding confidence score assignedto the first aspect being less than a predetermined threshold;configuring the wearable device, by the computing device, in accordancewith the first aspect in response to receiving confirmation of the firstaspect indicated by the request; and configuring the wearable device, bythe computing device, in accordance with a second aspect of the one ormore aspects in response to a determination that a correspondingconfidence score assigned to the second aspect is at least equal to thepredetermined threshold.
 7. The method as recited in claim 1, whereinthe one or more aspects of the wearable device comprise a physicalorientation of the wearable device with respect to a body part of a useron which the wearable device is coupled, the method further comprising:determining, by the computing device, that the physical orientation ofthe wearable device is not optimized for the user; and causing displayof an indication, by the computing device, that describes at least onecorrection to the physical orientation of the wearable device for theuser to implement.
 8. The method as recited in claim 1, wherein the oneor more aspects of the wearable device is selected from a groupconsisting of: a manufacturer and model of the wearable device, a sizeof the wearable device, a tightness of a band of the wearable device ona body part of a user, a material of the wearable device, a material ofthe band of the wearable device, a color of the wearable device, and acolor of the band of the wearable device.
 9. The method as recited inclaim 1, wherein the analyzing the one or more images to determine theone or more aspects of the wearable device comprises: detecting agraphical code displayed on the wearable device; and analyzing thegraphical code to determine the one or more aspects of the wearabledevice.
 10. A non-transitory computer-readable medium including one ormore sequences of instructions that, when executed by one or moreprocessors, cause the one or more processors to perform operationscomprising: receiving, by the one or more processors, one or more imagescorresponding to a wearable device; analyzing, by the one or moreprocessors, the one or more images to determine one or more aspects ofthe wearable device; and configuring, by the one or more processors, thewearable device using the one or more aspects of the wearable device.11. The non-transitory computer-readable medium as recited in claim 10,wherein the operations further comprise receiving, by the one or moreprocessors, indication that the wearable device has started a pairingprocess with a second electronic device prior to receiving the one ormore images corresponding to the wearable device, wherein the one ormore images corresponding to the wearable device include at least oneimage of the wearable device positioned on a body part of a user. 12.The non-transitory computer-readable medium as recited in claim 11,wherein the wearable device is a smartwatch and the body part is a wristof the user, and wherein the one or more aspects of the wearable deviceare selected from a group consisting of: a determination of which wristof the user the smartwatch is being worn on, a determination of whetherthe smartwatch is positioned on an inside or an outside of the wrist ofthe user, and a determination of an orientation of a crown of thesmartwatch.
 13. The non-transitory computer-readable medium as recitedin claim 10, wherein the one or more aspects of the wearable devicecomprise an orientation of a physical input element of the wearabledevice with respect to a body of the wearable device.
 14. Thenon-transitory computer-readable medium as recited in claim 10, whereinthe analyzing the one or more images to determine the one or moreaspects of the wearable device comprises assigning a confidence score toeach of the one or more aspects of the wearable device subsequent todetermination of the one or more aspects of the wearable device.
 15. Thenon-transitory computer-readable medium as recited in claim 14, whereinthe operations further comprise: causing display, by the one or moreprocessors, of a request to confirm a first aspect of the one or moreaspects in response to a corresponding confidence score assigned to thefirst aspect being less than a predetermined threshold; configuring thewearable device, by the one or more processors, in accordance with thefirst aspect in response to receiving confirmation of the first aspectindicated by the request; and configuring the wearable device, by theone or more processors, in accordance with a second aspect of the one ormore aspects in response to a determination that a correspondingconfidence score assigned to the second aspect is at least equal to thepredetermined threshold.
 16. The non-transitory computer-readable mediumas recited in claim 10, wherein the one or more aspects of the wearabledevice comprise a physical orientation of the wearable device withrespect to a body part of a user on which the wearable device iscoupled, wherein the operations further comprise: determining, by theone or more processors, that the physical orientation of the wearabledevice is not optimized for the user; and causing display of anindication, by the one or more processors, that describes at least onecorrection to the physical orientation of the wearable device for theuser to implement.
 17. The non-transitory computer-readable medium asrecited in claim 10, wherein the one or more aspects of the wearabledevice is selected from a group consisting of: a manufacturer and modelof the wearable device, a size of the wearable device, a tightness of aband of the wearable device on a body part of a user, a material of thewearable device, a material of the band of the wearable device, a colorof the wearable device, and a color of the band of the wearable device.18. The non-transitory computer-readable medium as recited in claim 10,wherein the analyzing the one or more images to determine the one ormore aspects of the wearable device comprises: detecting a graphicalcode displayed on the wearable device; and analyzing the graphical codeto determine the one or more aspects of the wearable device.
 19. Asystem comprising: one or more processors; and a non-transitorycomputer-readable medium including one or more sequences of instructionsthat, when executed by the one or more processors, cause the one or moreprocessors to perform operations comprising: receiving, by the one ormore processors, one or more images corresponding to a wearable device;analyzing, by the one or more processors, the one or more images todetermine one or more aspects of the wearable device; and configuring,by the one or more processors, the wearable device using the one or moreaspects of the wearable device.
 20. The system as recited in claim 19,wherein the operations further comprise: causing display, by the one ormore processors, of a request to confirm a first aspect of the one ormore aspects in response to a corresponding confidence score assigned tothe first aspect being less than a predetermined threshold; configuringthe wearable device, by the one or more processors, in accordance withthe first aspect in response to receiving confirmation of the firstaspect indicated by the request; and configuring the wearable device, bythe one or more processors, in accordance with a second aspect of theone or more aspects in response to a determination that a correspondingconfidence score assigned to the second aspect is at least equal to thepredetermined threshold.